User interface displaying and processing method and user interface displaying and processing device

ABSTRACT

The present disclosure provides a user interface displaying and processing method comprising following steps: applying Surface from a SurfaceFlinger to serve as a drawing board for drawing an interface; binding an OpenGL ES after being initialized and the Surface which is applied to server as the drawing board; controlling a function of the OpenGL ES to draw the interface on the Surface which is applied to server as the drawing board; after the interface has already been drawn, combining all Surfaces to form drawing board window data and exchanging the drawing board window data with display frame buffer window data; outputting to display the exchanged display frame buffer window data. The present disclosure further provides a user interface displaying and processing device. The present disclosure can improve the portability of applications.

TECHNICAL FIELD

The subject matter relates to television technology, and particularly,to a user interface displaying and processing method and a userinterface displaying and processing device.

DESCRIPTION OF RELATED ART

It is well-known that Android system comprises Linux kernel, Library,Dalvik virtual machine, and Android application framework. In anintelligent television system, Android applications usually drawgraphical interfaces based on the Dalvik virtual machine and the Androidapplication framework, thus making the applications to have a highdependency and a low portability.

BRIEF SUMMARY OF THE DISCLOSURE

A main object of the present disclosure is to provide a user interfacedisplaying and processing method and a user interface displaying andprocessing system which can improve the portability of the applications.

To achieve that, the present disclosure provides a user interfacedisplaying and processing method comprising following steps:

applying Surface from a SurfaceFlinger to serve as a drawing board fordrawing an interface;

binding an OpenGL ES after being initialized and the Surface which isapplied to server as the drawing board;

controlling a function of the OpenGL ES to draw the interface on theSurface which is applied to server as the drawing board;

after the interface has already been drawn, combining all Surfaces toform drawing board window data and exchanging the drawing board windowdata with display frame buffer window data;

outputting to display the exchanged display frame buffer window data.

Preferably, the step of “controlling a function of the OpenGL ES to drawthe interface on the Surface which is applied to server as the drawingboard” further comprises following steps:

controlling the function of the OpenGL ES to draw graphics, by a graphicfunction of the OpenGL ES, on the Surface which is applied to server asthe drawing board to form the interface; or

controlling the function of the OpenGL ES to map, by texture mapping, onthe Surface which is applied to server as the drawing board to form theinterface.

Preferably, when the function of the OpenGL ES is controlled to draw theinterface, the interface is dynamically displayed by a number ofinterface graphics, or the interface is dynamically displayed by renderchanging of OpenGL ES.

Preferably, the user interface displaying and processing method furthercomprises following steps:

establishing a communication mechanism with a preset shell application;

receiving and processing operation information transmitted by the shellapplication, the operation information being input information receivedby the shell application and commands from a preset window manager.

Preferably, the user interface displaying and processing method furthercomprises following steps:

when a user interface displaying command is detected, calling a show( )function to display an interface corresponding to the display framebuffer window data;

when a user interface hiding command is detected, calling a hide( )function to hide an interface corresponding to the display frame bufferwindow data.

In addition, to achieve that, the present disclosure further provides auser interface displaying and processing device comprising:

a drawing board applying module configured to apply Surface from aSurfaceFlinger to serve as a drawing board for drawing an interface;

a binding module configured to bind an OpenGL ES after being initializedand the Surface which is applied to server as the drawing board;

a control module configured to control a function of the OpenGL ES todraw the interface on the Surface which is applied to server as thedrawing board;

a data exchanging module configured to combine all Surfaces to formdrawing board window data and exchange the drawing board window datawith display frame buffer window data after the interface has alreadybeen drawn;

an outputting module configured to output to display the exchangeddisplay frame buffer window data.

Preferably, the control module is configured to:

control the function of the OpenGL ES to draw graphics, by a graphicfunction of the OpenGL ES, on the Surface which is applied to server asthe drawing board to form the interface; or

control the function of the OpenGL ES to map, by texture mapping, on theSurface which is applied to server as the drawing board to form theinterface.

Preferably, the control module is further configured to dynamicallydisplay the interface by a number of interface graphics or dynamicallydisplay the interface by render changing of OpenGL ES, when the functionof the OpenGL ES is controlled to draw the interface.

Preferably, the user interface displaying and processing device furthercomprises:

a communication module configured to establish a communication mechanismwith a preset shell application;

a receiving module configured to receive and process operationinformation transmitted by the shell application, the operationinformation being input information received by the shell applicationand commands from a preset window manager.

Preferably, the user interface displaying and processing device furthercomprises:

a calling module configured to call a show( ) function to display aninterface corresponding to the display frame buffer window data when auser interface displaying command is detected; and call a hide( )function to hide an interface corresponding to the display frame bufferwindow data when a user interface hiding command is detected.

The present disclosure applies Surface from a SurfaceFlinger to serve asa drawing board for drawing an interface; binding an OpenGL ES afterbeing initialized and the Surface which is applied to server as thedrawing board; controlling a function of the OpenGL ES to draw theinterface on the Surface which is applied to server as the drawingboard; after the interface has already been drawn, combining allSurfaces to form drawing board window data and exchanging the drawingboard window data with display frame buffer window data; outputting todisplay the exchanged display frame buffer window data. Since thedrawing and displaying of the user interface of the present disclosureis independent of the Android application framework and the Dalvikvirtual machine, the portability of the application is improved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flowchart of an embodiment of a user interface displayingand processing method.

FIG. 2 is a flowchart of another embodiment of a user interfacedisplaying and processing method.

FIG. 3 is a block diagram of an embodiment of a user interfacedisplaying and processing device.

FIG. 4 is a block diagram of another embodiment of a user interfacedisplaying and processing device.

FIG. 5 is block diagram of yet another embodiment of a user interfacedisplaying and processing device.

The technical solution of the present invention is hereinafter describedin detail with reference to the accompanying drawings.

DETAILED DESCRIPTION

It should be appreciate that the embodiments described herein are onlyintended to illustrate, but not to limit the present disclosure.

The main object of the present disclosure is to draw a user interface(UI) independent of the Android application framework and the Dalvikvirtual machine. Furthermore, the user interface can be drawnindependently, and also can be drawn seamlessly with the Androidapplication framework. The user can operate it just like he or she isoperating a common application. The user interface can be immediatelydisplayed when the user interface is needed to be displayed, and alsocan be immediately hided when the user interface is needed to be hided.

FIG. 1 illustrates that a user interface displaying and processingmethod comprises following steps:

At step S10, applying Surface from a SurfaceFlinger to serve as adrawing board for drawing an interface;

Since the user interface is drawn on a screen of a terminal, thus, adrawing board on which the user interface can be drawn is needed to beapplied. The drawing board can be a frame buffer of hardware or adisplay object managed by an operation system. Since the user interfaceof the present disclosure is needed to be drawn seamlessly with theAndroid application framework, thus, the user interface displaying andprocessing method of the present disclosure applies the Surface from theSurfaceFlinger to serve as the drawing board for drawing the interface.

At step S20, binding an OpenGL ES after being initialized and theSurface which is applied to server as the drawing board;

In detail, OpenGLES (OpenGL for Embedded Systems) includes subsets ofthe OpenGL 3D Graphics API, and is designed according to embeddeddevices such as mobile phones, personal digital assistant (PDA), andgame servers. The API is designed and promoted by Khronos Group. TheKhronos Group is a graphic software and hardware industrial associationwhich focuses on creating open standards for graphics and multimedia.OpenGL ES is a royalty-free and cross-platform API for full-function 2Dand 3D graphics on embedded systems-including consoles, mobile phones,hand-held devices, appliances, and vehicles. It consists of well-definedsubsets of desktop OpenGL, creating a flexible and powerful low-levelinterface between software and graphics acceleration. OpenGL ES includesprofiles for floating-point and fixed-point systems, and the EGLspecification for portably binding to native windowing systems. OpenGLES 1.X is designed according to fixed function hardware and offersacceleration, image quality, and performance. OpenGL ES 2.X enables fullprogrammable 3D graphics including cover devices.

When OpenGLES and the Surface are bounded, OpenGLES can communicate withthe window system of the local system, thereby allowing the mathematicalgraphic operations of OpenGLES to be displayed on the Surface. Beforeoperating OpenGLES, OpenGLES is needed to be initialized. After beinginitialized, OpenGLES and the Surface are bounded.

At step S30, controlling a function of the OpenGL ES to draw theinterface on the Surface which is applied to server as the drawingboard;

In the embodiment, the interface is drawn by the function of OpenGLES.In detail, when the interface is drawn, the function of OpenGLES isdirectly used to draw graphics on the Surface to form the userinterface. It is understandable that when the interface is drawn, thegraphic function of OpenGLES or texture mapping can be used. That is, inthe embodiment, the step S30 further comprises: controlling the functionof the OpenGL ES to draw graphics, by a graphic function of the OpenGLES, on the Surface which is applied to server as the drawing board toform the interface; or controlling the function of the OpenGL ES to map,by texture mapping, on the Surface which is applied to server as thedrawing board to form the interface.

At step S40, after the interface has already been drawn, combining allSurfaces to form drawing board window data and exchanging the drawingboard window data with display frame buffer window data;

At step S50, outputting to display the exchanged display frame bufferwindow data.

In the embodiment, when a user interface has already been drawn, data isexchanged between display frame buffer window and drawing board window,thereby combining all the Surface to form the drawing board window datawhich is transferred to frame buffer window, that is, the drawing boardwindow data is stored in a graphic memory; finally, the data in thegraphic memory is output to display, thus the user interface can bedisplayed. In detail, a display chip can directly process the data ofthe frame buffer window, convert pixel signals if necessary, and outputdetail pixel signals to the screen. The screen can display thecorresponding pixel according to the pixel signals.

The present disclosure applies Surface from a SurfaceFlinger to serve asa drawing board for drawing an interface; binding an OpenGL ES afterbeing initialized and the Surface which is applied to server as thedrawing board; controlling a function of the OpenGL ES to draw theinterface on the Surface which is applied to server as the drawingboard; after the interface has already been drawn, combining allSurfaces to form drawing board window data and exchanging the drawingboard window data with display frame buffer window data; outputting todisplay the exchanged display frame buffer window data. Since thedrawing and displaying of the user interface of the present disclosureis independent of the Android application framework and the Dalvikvirtual machine, the portability of the application is improved.

Furthermore, in the embodiment, when the function of the OpenGL ES iscontrolled to draw the interface, the interface is dynamically displayedby a number of interface graphics, or the interface is dynamicallydisplayed by render changing of OpenGL ES.

In detail, in the embodiment, the user interface can be statically ordynamically displayed. When the user interface is dynamically displayed,a number of interface graphics are used, or the render changing ofOpenGL ES is used. For example, when a number of interface graphics areused to dynamically display the user interface, the interface isperiodically drawn on the Surface which is applied to serve as thedrawing board at a preset time interval, all Surface are combined toform the drawing board window data, the drawing board window data isexchanged with the display frame buffer window data, and the exchangeddisplay frame buffer window data is output to display, therebydynamically displaying the user interface. When the rendering changingof OpenGLES is used to dynamically display the user interface, theinterface drawn on the Surface is periodically rendered at a preset timeinterval to obtain different effects, all Surface are combined to formthe drawing board window data, the drawing board window data isexchanged with the display frame buffer window data, and the exchangeddisplay frame buffer window data is output to display, therebydynamically displaying the user interface.

Furthermore, referring to FIG. 2, in the embodiment, the user interfacedisplaying and processing method further comprises:

At step S60, establishing a communication mechanism with a preset shellapplication;

At step S70, receiving and processing operation information transmittedby the shell application, the operation information being inputinformation received by the shell application and commands from a presetwindow manager.

Since the user interface displaying and processing method of the presentdisclosure is independent of the Android application framework and theDalvik virtual machine, thus, running the target applicationcorresponding to the user interface displaying and processing method ofthe present disclosure on the Android system may cause incompatibilitiesof inputs and incompatibilities of outputs, mainly of button input,touch input, and window display controls. Taking remote button inputsfor example, if the target application receives the remote buttoninputs, the Android application can also receive the remote buttoninputs. The reason for the incompatibilities is that the targetapplication is not created by the Android application framework, thus,the window manager of the Android system doesn't know the existence ofthe target application.

To solve the above problem, the present disclosure first creates acommon Android application which has no interface contents and appearsas transparent (that is the shell application in the presentdisclosure). The shell application can receive inputs signals and outputsignals just like a common Android application, and can be controlled bythe window manager. In the embodiment, the target application can firstestablish SOCKET communication mechanism with the shell application. Theshell application can transmit the input signal and the commands fromthe window manager to the target application. The target application canprocess the input signals and the commands, thereby allowing the targetapplication to be seamlessly run with the Android application framework.

Furthermore, in the embodiment, the user interface displaying andprocessing method further comprises following steps:

when a user interface displaying command is detected, calling a show( )function to display an interface corresponding to the display framebuffer window data;

when a user interface hiding command is detected, calling a hide( )function to hide an interface corresponding to the display frame bufferwindow data.

In the embodiment, the show( ) function and the hide( ) function areembedded application programming interface functions other thanfunctions of the Android system. The Android system calls the show( )function and the hide( ) function through the shell application, therebydisplaying and hiding the user interface. The application of the presentdisclosure can act as a common Android system which can be called by theAndroid system, and the compatibilities are improved.

The present disclosure further provides a user interface displaying andprocessing device. FIG. 3 illustrates that the user interface displayingand processing device comprises:

a drawing board applying module 10 configured to apply Surface from aSurfaceFlinger to serve as a drawing board for drawing an interface;

Since the user interface is drawn on a screen of a terminal, thus, adrawing board on which the user interface can be drawn is needed to beapplied. The drawing board can be a frame buffer of hardware or adisplay object managed by an operation system. Since the user interfaceof the present disclosure is needed to be drawn seamlessly with theAndroid application framework, thus, the user interface displaying andprocessing method of the present disclosure applies the Surface from theSurfaceFlinger to serve as the drawing board for drawing the interface.

a binding module 20 configured to bind an OpenGL ES after beinginitialized and the Surface which is applied to server as the drawingboard;

In detail, the OpenGLES (OpenGL for Embedded Systems) includes subsetsof the OpenGL 3D Graphics API, and is designed according to embeddeddevices such as mobile phones, personal digital assistant (PDA), andgame servers. The API is designed and promoted by Khronos Group. TheKhronos Group is a graphic software and hardware industrial associationwhich focuses on creating open standards for graphics and multimedia.OpenGL ES is a royalty-free and cross-platform API for full-function 2Dand 3D graphics on embedded systems-including consoles, mobile phones,hand-held devices, appliances, and vehicles. It consists of well-definedsubsets of desktop OpenGL, creating a flexible and powerful low-levelinterface between software and graphics acceleration. OpenGL ES includesprofiles for floating-point and fixed-point systems, and the EGLspecification for portably binding to native windowing systems. OpenGLES 1.X is designed according to fixed function hardware and offersacceleration, image quality, and performance. OpenGL ES 2.X enables fullprogrammable 3D graphics including cover devices.

When OpenGLES and the Surface are bounded, OpenGLES can communicate withthe window system of the local system, thereby allowing the mathematicalgraphic operations of OpenGLES to be displayed on the Surface. Beforeoperating OpenGLES, OpenGLES is needed to be initialized. After beinginitialized, OpenGLES and the Surface are bounded.

a control module 30 configured to control a function of the OpenGL ES todraw the interface on the Surface which is applied to server as thedrawing board;

In the embodiment, the interface is drawn by the function of OpenGLES.In detail, when the interface is drawn, the function of OpenGLES isdirectly used to draw graphics on the Surface to form the userinterface. It is understandable that when the interface is drawn, thegraphic function of OpenGLES or texture mapping can be used. That is, inthe embodiment, the step S30 further comprises: controlling the functionof the OpenGL ES to draw graphics, by a graphic function of the OpenGLES, on the Surface which is applied to server as the drawing board toform the interface; or controlling the function of the OpenGL ES to map,by texture mapping, on the Surface which is applied to server as thedrawing board to form the interface.

a data exchanging module 40 configured to combine all Surfaces to formdrawing board window data and exchange the drawing board window datawith display frame buffer window data after the interface has alreadybeen drawn;

an outputting module 50 configured to output to display the exchangeddisplay frame buffer window data.

In the embodiment, when a user interface has already been drawn, data isexchanged between display frame buffer window and drawing board window,thereby combining all the Surface to form the drawing board window datawhich is transferred to frame buffer window, that is, the drawing boardwindow data is stored in a graphic memory; finally, the data in thegraphic memory is output to display, thus the user interface can bedisplayed. In detail, a display chip can directly process the data ofthe frame buffer window, convert pixel signals if necessary, and outputdetail pixel signals to the screen if necessary. The screen can displaythe corresponding pixel according to the pixel signals.

The present disclosure applies Surface from a SurfaceFlinger to serve asa drawing board for drawing an interface; binding an OpenGL ES afterbeing initialized and the Surface which is applied to server as thedrawing board; controlling a function of the OpenGL ES to draw theinterface on the Surface which is applied to server as the drawingboard; after the interface has already been drawn, combining allSurfaces to form drawing board window data and exchanging the drawingboard window data with display frame buffer window data; outputting todisplay the exchanged display frame buffer window data. Since thedrawing and displaying of the user interface of the present disclosureis independent of the Android application framework and the Dalvikvirtual machine, the portability of the application is improved.

Furthermore, in the embodiment, when the function of the OpenGL ES iscontrolled to draw the interface, the interface is dynamically displayedby a number of interface graphics, or the interface is dynamicallydisplayed by render changing of OpenGL ES.

In detail, in the embodiment, the user interface can be statically ordynamically displayed. When the user interface is dynamically display, anumber of interface graphics are used, or the render changing of OpenGLES is used. For example, when a number of interface graphics are used todynamically display the user interface, the interface is periodicallydrawn on the Surface which is applied to serve as the drawing board at apreset time interval, all Surface are combined to form the drawing boardwindow data, the drawing board window data is exchanged with the displayframe buffer window data, and the exchanged display frame buffer windowdata is output to display, thereby dynamically displaying the userinterface. When the rendering changing of OpenGLES is used todynamically display the user interface, the interface drawn on theSurface is periodically rendered at a preset time interval to obtaindifferent effects, all Surface are combined to form the drawing boardwindow data, the drawing board window data is exchanged with the displayframe buffer window data, and the exchanged display frame buffer windowdata is output to display, thereby dynamically displaying the userinterface.

Furthermore, referring to FIG. 4, in the embodiment, the user interfacedisplaying and processing device further comprises:

a communication module 60 configured to establish a communicationmechanism with a preset shell application;

a receiving module 70 configured to receive and process operationinformation transmitted by the shell application, the operationinformation being input information received by the shell applicationand commands from a preset window manager.

Since the user interface displaying and processing method of the presentdisclosure is independent of the Android application framework and theDalvik virtual machine, thus, running the target applicationcorresponding to the user interface displaying and processing method ofthe present disclosure on the Android system may cause incompatibilitiesof inputs and incompatibilities of outputs, mainly of button input,touch input, and window display controls. Taking remote button inputsfor example, if the target application receives the remote buttoninputs, the Android application can also receive the remote buttoninputs. The reason for the incompatibilities is that the targetapplication is not created by the Android application framework, thus,the window manager of the Android system doesn't know the existence ofthe target application.

To solve the above problem, the present disclosure first creates acommon Android application which has no interface contents and appearsas transparent (that is the shell application in the presentdisclosure). The shell application can receive inputs signals and outputsignals just like a common Android application, and can be controlled bythe window manager. In the embodiment, the target application can firstestablish SOCKET communication mechanism with the shell application. Theshell application can transmit the input signal and the commands fromthe window manager to the target application. The target application canprocess the input signals and the commands, thereby allowing the targetapplication to be seamlessly run with the Android application framework.

Furthermore, referring to FIG. 5, in the embodiment, the user interfacedisplaying and processing device further comprises:

a calling module 80 configured to call a show( ) function to display aninterface corresponding to the display frame buffer window data when auser interface displaying command is detected; and call a hide( )function to hide an interface corresponding to the display frame bufferwindow data when a user interface hiding command is detected;

In the embodiment, the show( ) function and the hide( ) function areembedded application programming interface functions other thanfunctions of the Android system. The Android system calls the show( )function and the hide( ) function through the shell application, therebydisplaying and hiding the user interface. The application of the presentdisclosure can act as a common Android system which can be called by theAndroid system, and the compatibilities are improved.

What described above are only preferred embodiments of the presentdisclosure but are not intended to limit the scope of the presentdisclosure. Accordingly, any equivalent structural or process flowmodifications that are made on basis of the specification and theattached drawings or any direct or indirect applications in othertechnical fields shall also fall within the scope of the presentdisclosure.

What is claimed is:
 1. A user interface displaying and processing methodcomprising following steps: applying Surface from a SurfaceFlinger toserve as a drawing board for drawing an interface; binding an OpenGL ESafter being initialized and the Surface which is applied to server asthe drawing board; controlling a function of the OpenGL ES to draw theinterface on the Surface which is applied to server as the drawingboard; after the interface has already been drawn, combining allSurfaces to form drawing board window data and exchanging the drawingboard window data with display frame buffer window data; outputting todisplay the exchanged display frame buffer window data.
 2. The userinterface displaying and processing method of claim 1, wherein the stepof “controlling a function of the OpenGL ES to draw the interface on theSurface which is applied to server as the drawing board” furthercomprises following steps: controlling the function of the OpenGL ES todraw graphics, by a graphic function of the OpenGL ES, on the Surfacewhich is applied to server as the drawing board to form the interface;or controlling the function of the OpenGL ES to map, by texture mapping,on the Surface which is applied to server as the drawing board to formthe interface.
 3. The user interface displaying and processing method ofclaim 2, wherein when the function of the OpenGL ES is controlled todraw the interface, the interface is dynamically displayed by aplurality of interface graphics, or the interface is dynamicallydisplayed by render changing of OpenGL ES.
 4. The user interfacedisplaying and processing method of claim 1, further comprisingfollowing steps: establishing a communication mechanism with a presetshell application; receiving and processing operation informationtransmitted by the shell application, the operation information beinginput information received by the shell application and commands from apreset window manager.
 5. The user interface displaying and processingmethod of claim 1, further comprising following steps: when a userinterface displaying command is detected, calling a show( ) function todisplay an interface corresponding to the display frame buffer windowdata; when a user interface hiding command is detected, calling a hide() function to hide an interface corresponding to the display framebuffer window data.
 6. The user interface displaying and processingmethod of claim 5, wherein the step of “controlling a function of theOpenGL ES to draw the interface on the Surface which is applied toserver as the drawing board” further comprises following steps:controlling the function of the OpenGL ES to draw graphics, by a graphicfunction of the OpenGL ES, on the Surface which is applied to server asthe drawing board to form the interface; or controlling the function ofthe OpenGL ES to map, by texture mapping, on the Surface which isapplied to server as the drawing board to form the interface.
 7. Theuser interface displaying and processing method of claim 6, wherein whenthe function of the OpenGL ES is controlled to draw the interface, theinterface is dynamically displayed by a plurality of interface graphics,or the interface is dynamically displayed by render changing of OpenGLES.
 8. The user interface displaying and processing method of claim 5,further comprising following steps: establishing a communicationmechanism with a preset shell application; receiving and processingoperation information transmitted by the shell application, theoperation information being input information received by the shellapplication and commands from a preset window manager.
 9. A userinterface displaying and processing device comprising: a drawing boardapplying module configured to apply Surface from a SurfaceFlinger toserve as a drawing board for drawing an interface; a binding moduleconfigured to bind an OpenGL ES after being initialized and the Surfacewhich is applied to server as the drawing board; a control moduleconfigured to control a function of the OpenGL ES to draw the interfaceon the Surface which is applied to server as the drawing board; a dataexchanging module configured to combine all Surfaces to form drawingboard window data and exchange the drawing board window data withdisplay frame buffer window data after the interface has already beendrawn; an outputting module configured to output to display theexchanged display frame buffer window data.
 10. The user interfacedisplaying and processing device of claim 9, wherein the control moduleis configured to: control the function of the OpenGL ES to drawgraphics, by a graphic function of the OpenGL ES, on the Surface whichis applied to server as the drawing board to form the interface; orcontrol the function of the OpenGL ES to map, by texture mapping, on theSurface which is applied to server as the drawing board to form theinterface.
 11. The user interface displaying and processing device ofclaim 10, wherein the control module is further configured todynamically display the interface by a plurality of interface graphicsor by render changing of OpenGL ES, when the function of the OpenGL ESis controlled to draw the interface.
 12. The user interface displayingand processing device of claim 9, further comprising: a communicationmodule configured to establish a communication mechanism with a presetshell application; a receiving module configured to receive and processoperation information transmitted by the shell application, theoperation information being input information received by the shellapplication and commands from a preset window manager.
 13. The userinterface displaying and processing device of claim 9, furthercomprising: a calling module configured to call a show( ) function todisplay an interface corresponding to the display frame buffer windowdata when a user interface displaying command is detected; and call ahide( ) function to hide an interface corresponding to the display framebuffer window data when a user interface hiding command is detected. 14.The user interface displaying and processing device of claim 13, whereinthe control module is configured to: control the function of the OpenGLES to draw graphics, by a graphic function of the OpenGL ES, on theSurface which is applied to server as the drawing board to form theinterface; or control the function of the OpenGL ES to map, by texturemapping, on the Surface which is applied to server as the drawing boardto form the interface.
 15. The user interface displaying and processingdevice of claim 14, wherein the control module is configured todynamically display the interface by a plurality of interface graphicsor by render changing of OpenGL ES, when the function of the OpenGL ESis controlled to draw the interface.
 16. The user interface displayingand processing device of claim 13, further comprising: a communicationmodule configured to establish a communication mechanism with a presetshell application; a receiving module configured to receive and processoperation information transmitted by the shell application, theoperation information being input information received by the shellapplication and commands from a preset window manager.